Some Final Notes on the NetWare Asynch Router TD.S.ARO10 July 20, 1993 NetWare Asynch Router VERSION: All SUPERSEDES: All Prior NetWare Asynch Router Documents OVERVIEW The NetWare Asynchronous Router was provided to NetWare LAN owners for several years, both as a separate product and, with some versions of NetWare, as a "free utility". We realized several months ago that the code on which the NetWare Asynch Router is based had become obsolete and we therefore, discontinued its sale. In late March, 1993 free distribution was also discontinued. We recognize that the Asynch Router served needs that many of our customers find important. - an external asynch IPX router - An internal asynch IPX router - An asynchronous ODI or IPX connection for remote workstations. We are currently developing products which will meet those needs and will offer them for sale in the not too distant future. The Asynch Router was never robust nor fast. - It is not recommended for mission critical applications. - It is too slow to be practical for large file transfers. - It is much too slow to be practical for remote use of applications. That is, if you try to load an application from a remote site, so much time will go by that you will think your computer has locked. For the remote use of an application, products like Novell's Access server which transmit only keystrokes and screen updates are recommended instead. - NOTE: the Async Router can not run in a NetWare 3.x or NetWare 4.x server. (internal router) This document is: - designed to provide a "do it yourself" primer for sites that already have the Asynch Router and choose to continue to use it. - based on the assumption that you already have either the: - manual that came with a copy of Asynch Router that you purchased. or - manuals from a purchased copy of NetWare 3.11 or NetWare 2.2. CONTENTS I. Versions II. Troubleshooting A. Addressing B. LAN F died C. invalid ID string D. Modems III. Features IV. Speed V. Recommendations VI. Router Installation VII. Router Configuration VIII. ODI Remote Workstation Installation IX. Sample NET.CFG for remote ODI workstation I. VERSIONS Some versions are not compatible with other versions. It is important that all of the NetWare Asynch Routers in your system be the same version. If you are installing a different version of the Router on a PC that has Asynch Router software already installed, you must delete the original version and reboot the PC before you install the new software. A. Problems in Early Versions 1. If two COMM ports were defined, errors occurred during the linking process. 2. If two WNIM+ adapters were configured in the same router, IPX packets were intermittently lost. 3. The "Timed Life Class" reported by LCONSOLE did not report the correct time. 4. The Timed Life Class feature did not function if set for more than one minute. 5. The modems sometimes did not reset after a disconnect. 6. Lconsole did not always reset the modems when dialing out. B. Limitations in Later Versions (including the last) - Protected Mode not available. - Remote workstation support is available only if ODI is used. - The Reset option of LCONSOLE does not operate correctly. - You can set Idle Time Out only to one minute. - When you configure an internal router with a WNIM+, the router will abort if the modem fails or you are using a modem that is not supported. - NetWare for the Macintosh is not supported across the Async Router. - All WNIM+ ports must be at same baud rate. - In the "Special Configuration" modem type, the "Modem Initialization String" option is not supported. Characters entered into this field are NOT sent to the modem. C. Number of Communication Lines Supported The final release of the Async Router supported a maximum of 9 communication lines (up to two WNIM+ four port adapters, and one COM port) plus One LAN adapter. II. TROUBLE SHOOTING -------------------------------- A. ADDRESSING Addressing mistakes are the main cause of problems. - Starting with version 1.2 all LAN addresses (including internal IPX addresses) MUST be unique. That is, all addresses, including the router addresses, on both LAN must be selected as though the two LANs together constitute a single LAN. Duplicate addresses cause many varied symptoms. Whether the router only acts a bit strangely or fails to operate at all, suspect a duplicate address. - Versions prior to 1.2 required the LAN address, only, on each side of the router to be identical. B. LAN F died This error message means the connection was broken. The asynch router is very sensitive to noise on the phone line. It is inevitable that you will occasionally, and perhaps frequently, receive this error message. C. INVALID ID STRING If the Router fails to link and the error message "Invalid ID String"is received please check the following: 1. When doing ACONFIG use the delete key to remove all ID strings and passwords. The ID string field may contain undisplayed characters. To be sure, hit the Delete key an extra time. 2. The modems may be receiving noise. - Have the telephone company check the lines. - Make certain the line does not have features like call waiting. 3. Try lowering the baud rate. D. MODEMS The router is very sensitive to modems. 1. Always use identical modems on both sides. 2. The router was designed when modems were much simpler than now. If you try to improve the routers performance by using an advanced modem with special features you are likely to end up with worse performance. 3. Data Compression tends to cause problems. Be prepared to disable Data Compression. 4. Version 1.2 of the router supported modems from Hayes, US Robotics, Telebit, and Ventel at speeds up to 9600bps. If such support is available, V.32 modems are recommended as a first choice. 5. If you are using a version earlier than 1.2, you must use a modem which is FULLY Hayes compatible. 6. Be wary of the term "Hayes Compatible", it has very limited meaning at speeds over 2400bps. Failure to set for Basic Hayes type responses could cause the router to hang. 7. Do not try to use modems that are not listed on the menu. 8. MNP Modem Configuration When using modems that support MNP protocols, the modem response codes should be set to Basic, not Extended. Example setting: Microcom: ATX0 9. If you selected "Hayes Compatible" and the connection fails to establish the modems may not be returning true Hayes codes. - They may not be set up properly. - Although "Hayes Compatible" they may not be able to do this. IV. SPEED - The absolute top speed of the router with a WNIM+ board is 19.2kbps. - The absolute top speed of the router without a WNIM+ board is 9600bps. - Even with a WNIM+, speeds BETWEEN 9600 and 19.2 are not available. (therefore 14.4 is not available) - Actual throughput will vary with line quality and hardware. V. RECOMMENDATIONS A. The router works most efficiently if a WNIM+ communication adapter is used. There is no other compatible communication adapter. WNIM+ boards are also compatible with Novell's NACS and Access Server products. B. We recommend an external dedicated router for optimum performance. You may use the PC as a nondedicated external router and also as a workstation on the LAN, but if you do so, you may not have sufficient memory to run applications on the workstation. The router software (ROUTER.EXE) takes up to 350KB of RAM, NET3 takes up about 20KB, and DOS takes up 40 to 60 KB, so as little as 170KB may be available for applications. C. For an internal router (one installed in a file server), we recommend a minimum of 4MB of RAM. The asynch router can be run as an internal router in NetWare 2.x file servers. However, we do not recommend internal asynch routers because the router is like to hang and cause the file server to lock. THE INFORMATION BELOW APPLIES TO THE LATER VERSIONS The router PC should meet the following minimum requirements: o Minimum of 512K RAM for a dedicated external router (real mode) o Minimum of 640K RAM for a nondedicated external router (real mode) o Minimum of 1MB RAM for a dedicated external router (protected mode) NOTE: Protected mode not available in latest versions. VI. ROUTER INSTALLATION 1. Copy the router files to a directory called LAN_DRV_190 or to a diskette with the volume label LAN_DRV_190. 2. *ACONFIG, ROUTER.EXE, and NACSLOAD.BIN must be together in a directory. *(ARCONFIG in early versions) 3. Copy LCONSOLE.EXE and the files it needs to operate properly ($V11.OVL, ERR$V11.DAT, HELP$V11.DAT, IBM$V11.OVL, LCONSOLE.HLP, and MSG$V11.DAT) to a directory available to LAN users (for example, PUBLIC). 4. Generate the Router. VII. ROUTER CONFIGURATION A. After generating the router, configure it using ACONFIG (prior to Version 1.2, ARCONFIG). We suggest that you configure the Router on a 12Mh or slower machine but move it to a faster machine for actual operation. If you receive a Configuration Error run DCONFIG ROUTER.EXE to check the parameters and addressing. Then use DCONFIG to make any required corrections. 1. For an External Router Run ACONFIG from where you ran LAN_DRV_190. The path to ROUTER.EXE must be less than 30 characters. a. Copy NACSLOAD.BIN to the same directory as ROUTER.EXE. b. Go to the directory containing ACONFIG c. *Type ACONFIG drive\pathname\ROUTER.EXE 2. For an Internal Router a. Copy NACSLOAD.BIN to the SYS:SYSTEM directory b. Go into the servers System directory and Flag NET$OS.EXE, Shareable, Read, Write (SRW). c. *Type ACONFIG NET$OS.EXE In both cases you will then get a PLEASE WAIT for several seconds. * NOTE: Speeds above 2400 BPS without a WNIM card are not supported. However, if you want to try 9600BPS and your computer has a 16550 UART it is possible that you will be successful. In order to configure for speeds over 2400 through a Comm port type: ACONFIG ROUTER.EXE F or ACONFIG NET$OS.EXE F Instead of ACONFIG ROUTER.EXE or ACONFIG NET$OS.EXE B. Then proceed through the ACONFIG menu configuring EACH router and EACH line for EACH driver selected during the router generation process. NOTE: Spaces may not be used in the Router Server name. NOTE: For an External Router each WNIM board or Com port must have a unique name. NOTE: All ports on a WNIM Board must be configured for the same Bits Per Second (BPS) rate. NOTE: The ID string must be EXACTLY the same as you will specify in LCONSOLE. (It is Case Sensitive) If you will not be specifying one in LCONSOLE it is VERY important that you not enter anything into this data field. NOTE: Select modem type "NONE" if you have a leased line. NOTE: This version of the software allows you to change the Modem Initialization String. NOTE: The WNIM must be the last LAN adapter configured in the router. NOTE: If you are using a US Robotics V.32 modem: - Choose US Robotics HST from the menu. - Change the modem initialization string from B1 to B0 and S13=32 to S34=7. C. Then escape out and save. D. Reboot the Router. E. If it is an Internal router change the Flag for NET$OS.EXE to Read Only. VIII. ODI Remote Workstation Installation NOTE: If your Asynch Router includes IPXODI.COM you can create an ODI remote workstation. If your Asynch Router includes SCOM.OBJ you can create an IPX remote workstation. 1. Create a directory containing: LSL.COM NARS.COM IPXODI.COM NETX.COM NET.CFG 2. NET.CFG is an ASCII file which will contain the configuration information. We have provided a sample NET.CFG which you should modify according to the needs of your environment. NET.CFG must contain two headings Link Support Link Driver NARD Under "Link Support" two statements are to be indented: Buffers MemPool Under "Link Driver NARD" the following statements are to be indented: Frame Ethernet_802.3 Protocol IPX 0 Ethernet_802.3 int #1 [interrupt level] port #1 [port address] other router id [astring] My Workstation Name [aname] baud rate [comm port speed in bits per second] modem type [a number from the table below] modem initialization string hardware flow control [0 or 1, see below] dial prefix [string to start dialing] dial number [the number to be dialed] Explanation Frame Ethernet_802.3 and Protocol IPX 0 Ethernet_802.3 At the present time IPX Ethernet 802.3 is the only protocol that should be used across the asynch router line. You should specify this even though the rest of your topology is Token Ring or Arcnet. int #1 Sets the Interrupt for port number 1. For Comm 1 int #1 4 For Comm 2 int #1 2 For Comm 3 int #1 [specify the number of the next available interrupt] For Comm 4 int #1 [specify the number of the next available interrupt] port #1 A hex number specifying the COM port for port #1. For COM1 port #1 3f8 For COM2 port #1 2f8 For COM3 port #1 [specify the I/O address of the next available port] For COM4 port #1 [specify the I/O address of the next available port] NOTE: Only one port can be specified (used) at a time. other router ID The ID string for the router on the other side of the line, if it has an id string. The maximum length is 10 characters and spaces. If you receive the error message "Invalid ID String" try deleting this field and the id string on the other side. my workstation name Any name up to a maximum of 48 characters and spaces. BAUD RATE The rate in bits per second that the comm port will be running at. The rate must be at least 1200 and not more than 19200. For US Robotics V32 or MultiModems by specifying 19200 bps you will be setting the maximum speed between the comm port and modem but the two modems will negotiate the best attainable speeds between one another. MODEM TYPE None (direct connect) 0 Hayes and compatibles 1 Telebit Ven\Tel PEP 2 Special Configuration 3 US Robotics Courier V32 4 US Robotics Courier 24PS 5 Multimodem V32 6 modem initialization string - maximum length of the string is 46 characters. - minimum length of the string is 0 (direct connect). Suggested modem initialization strings: Hayes and Hayes compatibles ATV0E0S0=1X1 Telebit ATV0E0S0=1S58=2S66=1 (for 9600 bps) US Robotics Courier V.32 ATE0&H1&R2&B1&M4V0Q0X1&A0S0=1S13=32 US Robotics Courier 24PS AT&B5VX1Q&AE&H1&R2&I&C1&D2 MultiModem ATEQV&QX4&E1&E4&E7&E10&E13&E15$BA$A1 (for MultiModem "Reliable Mode" and "Compression On" ) hardware flow control 1 for yes 0 for no dial prefix the string to start dialing - maximum length is 40 characters - this field MUST be filled out if the driver is to initiate the connection. It should "Remmed Out" for a direct connection. - Suggested prefix strings AT&R&C1DT for MultiModem for reliable and compression on ATV0DT for the other modems dial number - the phone number to call - maximum length is 40 characters - Use a comma for a pause - this field MUST be filled out if this driver is to initiate the connection. It should be "Remmed Out" for a direct connection. 2. TO LOAD Type at the command line LSL NARS IPXODI NETX 3. TO UNLOAD Unload in the reverse order of loading by typing at the command line: NET3 U IPXODI U NARS U 4. To RELOAD if the Connection fails Unload NETX, IPXODI, and NARS (see above) Then Type NARS IPXODI NETX IX. Sample NET.CFG for Remote ODI workstation Link Support Buffers 8 1586 MemPool 4096 Link Driver NARD Frame Ethernet_802.3 Protocol IPX 0 Ethernet_802.3 my workstation name orca int #1 4 port #1 3f8 baud rate in bps 19200 modem type 6 modem initialization string ateqv&qx4&e1&e4&e7&e10&e13&e15$ba$a1 hardware flow control 0 dial prefix at&r&c1dt dial number 9,8005551212 Note: See your NetWare manual for information regarding Buffers, Mempool and other available NET.CFG parameters.